The scheduled export task runs the Meridian Enterprise export processor to create briefcases for remote collaborating sites. A parameter in the command line of the task specifies which transfers to process.
The export processor command line should specify the following parameters:
If the configuration file is located in the same folder as the vault export processor, the path can be omitted.
Note Installing the processors as described in Installing the GCF components installs sample .cmd files for export and import with the correct configuration file names and share names that you can use to compose the command line.
Following is an example of a scheduled Meridian Enterprise export processor command line:
"C:\GCF\Meridian\Processors\GCFExportLauncher.exe" GCFProc.ini Scheduled
Note On Windows Server 2008, multiple instances of GCFExportProc.exe can exist for the same target share. The export processor starts and fails to find an existing instance. This can occur only when GCFExportLauncher.exe is used to export to all available shares.
To work around this issue, instead of scheduling two export tasks (one for scheduled execution and one for immediate execution), schedule two tasks for each destination share name. For example, assuming three GCF sites: SiteA, SiteB, and SiteC synchronized by two tasks with command lines similar to the following:
GCFExportLauncher.exe gcf.ini scheduled GCFExportLauncher.exe gcf.ini
Replace them with four tasks for each site with command lines similar to the following:
GCFExportProc.exe gcf.ini SiteB true GCFExportProc.exe gcf.ini SiteC true GCFExportProc.exe gcf.ini SiteB false GCFExportProc.exe gcf.ini SiteC false
The first two tasks perform SiteA scheduled updates, the second two tasks perform SiteA immediate updates. Create four similar tasks on each of SiteB and SiteC.